home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ShareWare OnLine 2
/
ShareWare OnLine Volume 2 (CMS Software)(1993).iso
/
elecmail
/
rnet200f.zip
/
UPGRADE.DOC
< prev
next >
Wrap
Text File
|
1993-06-02
|
9KB
|
173 lines
-------------------------------------------------------------------------------
Upgrading from RNET 1.xx to 2.00
-------------------------------------------------------------------------------
This document is here to tell you how to upgrade from an existing 1.xx
version of RNET to version 2.00. Please read the entire thing so you know
what to expect and how to enable some of the new features. Note that not
all features or functions are described -- that will have to wait for the
final documentation.
(1) Backup your existing RNET files (*.exe, *.cfg, etc). You aren't likely
ever going to need the old files, but you'll be very unhappy if you do
need them and you didn't make a backup. I recommend just making a quick
ZIP of the old files and putting it somewhere out of harms way.
(2) Put the new RNET.EXE where you want it (on the path or in \PCB or in a
RNET directory). From the old files, you want to keep:
MSGCOUNT.BIN (keeps global counters)
<hostid>.CFG (config file for each host)
<hostid>.PTR (pointer file for each host)
(3) Using Qedit or TSE or whatever text editor you prefer, add the following
to the top of your <hostid>.CFG files:
HOSTID=<hostid> ; (8 char 'ID' of your HOST system)
LOCALID=<yourid> ; (8 char 'ID' of YOUR system; for routing)
ROUTED=NO ; (disable extended ORIGIN and SEENBY lines)
In 1.xx, RNET used the <hostid> specified on the commandline to
determine the host name (for QWKs, REPs, and similar stuff). The new
version of RNET allows you to call the .CFG anything you want and uses
the HOSTID= specified within the .CFG to determine the host name.
The LOCALID= is used to tell RNET what your board's ID is in the mail
doors you have online. It is needed by RNET version 2 for mail routing.
The specified id would be what someone would need to enter to have
messages routed to your system. If you do not have a mail door id
already assigned to you, use the first 8 letters of your BBS name or
some other unique identification until you can contact me or the network
administration to get a unique id.
The ROUTED=NO is used to disable the extended ORIGIN and SEENBY lines
used by RNET. Use ROUTED=YES *when* the network you are echoing with
supports routed QWK mail. Until QWK packet based routed mail is in use
on the network in question, there is no point (other than informative)
for those extended lines. PCBoard 15.0 will "hide" those lines, but not
everyone is using PCBoard 15.0.
(4) If you use RNET= or QWIKMAIL= environment variables to point to a "home"
directory for RNET, make sure it is set.
Also, you should set a PCBDAT= environment variable to the full filename
of your PCBOARD.DAT file. If you run RNET.EXE with no params, it will
tell you what the current settings are for the RNET= and PCBDAT=
environment variables.
[added in 2.00f] - RNET will use the PCBDAT= environment to find the
directory or full filename of PCBOARD.DAT; then it will search the
current directory for PCBOARD.DAT; and finally, it will search the
entire DOS PATH= environment for PCBOARD.DAT.
(5) In order to convert your existing pointers (<hostid>.PTR) to the new
pointers (<hostid>.RPF), do a: RNET EXPORT <hostid>. When RNET needs
to create a new RPF file, it searches for an old PTR file to use for the
pointers. If the old PTR file is not found, RNET will "top" the new
pointers. Once you have a RPF file, you may delete your old PTR file.
If, for some reason, RNET didn't see your .PTR file (likely from it not
being in the "home" directory pointed to by RNET= environment), set the
environment as needed or copy the .PTR file to the current directory,
delete the .RPF, and do another RNET EXPORT <hostid>. You should get a
"notice" on the screen about "reading old pointer file...".
(6) Review the output placed in NOTICE.LOG, WARNING.LOG, and ERROR.LOG.
These files are created in the current or "home" directory.
NOTICE.LOG (things you should be aware of but aren't important)
WARNING.LOG (things that are important but aren't critical)
ERROR.LOG (something that caused RNET to fail--critical errors)
Expect in NOTICE.LOG:
List of conferences added to a new pointer file
List of old conference pointers read (and values therein)
List of conference messagebases created (if any were missing)
Expect in WARNING.LOG:
Warning about creating a new pointer file (hostid.RPF)
List of keywords "no longer supported" (yell if you need one of 'em)
(put a ; at the front of those keywords in the CFG to disable them)
If ERROR.LOG exists:
If it can't find PCBOARD.DAT, you need to set your PCBDAT= environ:
SET PCBDAT=C:\PCB\PCBOARD.DAT (the full pathname of PCBOARD.DAT)
Make any corrections or changes to your CFG files as recommended by the
logs. A lot of information will show up in these logs the first time
RNET is run (since it is configuring all the conferences, reading the
old pointer file, and similar things). You may delete any or all of
these logs when you have taken care of whatever they are warning you
about.
Don't worry if you see a "used old style conference config" message as
you haven't had a chance to change to the newer style. RNET will
continue to support the older style PRIVATE=, ANSI=, and similar
keywords as well as the new expanded CONF= statements.
(7) Add to your CFG: SWAPPATH=d:\dir\ (path where RNET can write swapfile)
The SWAPPATH= keyword will tell RNET where it can put a swap file when a
shell'ed to program runs out of memory. RNET will try using a shell
first -- if that fails (or an errorlevel is returned), it will swap
itself out of memory and try again.
Do *NOT* use the same temp directory for swapping that you use for
uncompressing/compressing packets. If you do, PKZIP may end up
trashing your .REP and the swap file (likely resulting in a lockup).
If SWAPPATH= is not specified, RNET will use the current directory.
(8) If running PKZIP version 2, check your COMPRESS= statement. If it
contains a "-m", *remove it*. The new version of PKZIP uses -m
differently than the old version in that it *deletes* the working
directory when it is done. I consider this a bug in PKZIP, but PKware
thinks it's a feature... go figure.
-------------------------------------------------------------------------------
Optional Things (enabling new features)
-------------------------------------------------------------------------------
(A) RNET uses the colors you have defined for PCBSM. If you want to
customize the display colors: (a) Make a backup of PCBSM.CLR; (b) use
PCBSM.EXE to change the colors as desired; (c) copy the new PCBSM.CLR to
the RNET directory and/or rename it to RNET.CLR; (d) restore your
origional PCBSM.CLR.
(B) To turn on "you have mail waiting" flags for users, add:
YOURMAIL=YES ; (enable 'you have mail waiting' flag updates)
(C) To turn on automatic backing up of QWK, REP and RPF files, use:
KEEPPATH=d:\dir\ ; (location for backup QWK, REP, RPF files)
KEEPQWKS=5 ; (number of QWK packets to keep in backup dir)
KEEPREPS=5 ; (number of REP packets to keep in backup dir)
KEEPRPFS=5 ; (number of RPF files to keep in backup dir)
Disable any of these by specifing zero (0). Max is currently 9.
Default KEEPPATH= is "keep\" under the current directory.
(D) To change the default AGE limit for messages from 30 days, use:
AGELIMIT=15 ; (max age in days of messages allowed)
(E) To enable refer-number support and host dup checking, use:
REFER=YES ; (enable REFER number support & dup checking)
CHECK_NUMBERS=YES ; (enable dup check of host message numbers)
(F) To enable CRC32 dup checking:
CHECK_CRC=YES ; (enable X.25 CRC32 dup ck; requires REFER=YES!)
(G) (see RNETPACK.DOC for instructions on enabling RNET's packing support)
To play with the other new features, refer to RNET_REF.DOC until RNET.DOC
is finished.
-------------------------------------------------------------------------------